Cream of the Crop 20/Cream of the Crop 20 (Terry Blount) (1996).iso/os2/lynxos25.zip/lynx_2.INF

OS/2 Help File | 1996-07-20 | 52KB | 1,568 lines

ΓòÉΓòÉΓòÉ 1. Lynx/2 Users Guide Introduction ΓòÉΓòÉΓòÉ

Lynx/2 is a fully-featured World Wide Web (WWW) client for OS/2 VIO sessions,
either windowed or full-screen. It will display hypertext markup language
(HTML) documents containing links to files residing on the local system, as
well as files residing on remote systems running Gopher, HTTP, FTP, WAIS, and
NNTP servers.

Lynx/2 can be used to access information on the World Wide Web, or to build
information systems intended primarily for local access. In addition, Lynx/2
can be used to build systems isolated within a single LAN.


ΓòÉΓòÉΓòÉ 2. Setting Up Lynx/2's CFG file ΓòÉΓòÉΓòÉ

The actual installation of the Lynx/2 package is covered in the Readme.os2
file. Please refer to that file for installation instructions.

This section will concern itself with changes that can or should be made to the
Lynx.CFG file, which Lynx/2 will look for in your $ETC directory.


ΓòÉΓòÉΓòÉ 2.1. General Considerations ΓòÉΓòÉΓòÉ

The default placement for this file is in the $ETC directory. Definition pairs
are of the form VARIABLE:DEFINITION. NO spaces are allowed between the pair
items. If you like, you may specify it's location on the command line with the
"-cfg" command line option.

Items may be commented out by putting a '#' as the FIRST char of the line All
definitions must be flush left and have NO spaces.!!!

All examples given here are from the Lynx.cfg files used here.


ΓòÉΓòÉΓòÉ 2.2. The STARTFILE Entry ΓòÉΓòÉΓòÉ

STARTFILE is the default URL if none is specified on the command line. These
files can be remote (http://www.w3.org/default.html) or local
(file://localhost/DIRECTORY/FILENAME).

Some examples (All but one commented out).

# STARTFILE:http://www.cc.ukans.edu/about_lynx/www_start.html
# STARTFILE:file:///e:/webpage/djd/index.html
STARTFILE:http://www.cris.com/~djd/

You will probably want to put your own startfile here.


ΓòÉΓòÉΓòÉ 2.3. The HELPFILE Entry ΓòÉΓòÉΓòÉ

HELPFILE must be defined as a URL and must have a complete local path name if
local (file://localhost/x:/DIRECTORY/FILENAME).

Examples are:

#HELPFILE:http://kufacts.cc.ukans.edu/lynx_help/lynx_help_main.html
HELPFILE:file://localhost/f:/lynx/help/lynx_hel.htm

You will probably want to update this to reflect the actual directory Lynx/2 is
installed in.


ΓòÉΓòÉΓòÉ 2.4. The JUMPFILE Entry ΓòÉΓòÉΓòÉ

JUMPFILE is the local file checked for shortcut URL's when the user presses the
'J' (JUMP) key. The user will be prompted for a shortcut entry (analogously to
'g'oto), and can enter one or use '?' for a list of the shortcuts with
associated links to their actual URL's. See the sample jumps files in the
samples subdirectory. Make sure your jumps file includes a '?' shortcut for a
file://localhost URL to itself:

<dt>?<dd><a href="file://localhost/path/jumps.html">This Shortcut List</a>

If not defined here, the JUMP command will invoke the NO_JUMPFILE statusline
message.

Do not include "file://localhost" in the definition. An example would be:

JUMPFILE:/Lynx_Dir/jumps.html


ΓòÉΓòÉΓòÉ 2.5. The CHARACTER_SET entry ΓòÉΓòÉΓòÉ

The CHARACTER_SET defines the users default 8 bit character set which is used
to represent the list of character entities within HTML.

The default character sets include:

     ISO Latin 1

     DEC Multinational

     IBM PC character set

     NeXT character set

     7 bit approximations

 An example would be as follows, which is recommended for Lynx/2:

  CHARACTER_SET:IBM PC character set


ΓòÉΓòÉΓòÉ 2.6. The BOLD_HEADERS Entry ΓòÉΓòÉΓòÉ

If BOLD_HEADERS is set to TRUE the HT_BOLD default style will be acted upon for
<H1> through <H7> headers. The default is FALSE (only the uppercasing and
indentation styles are acted upon).

An Example:

BOLD_HEADERS:FALSE


ΓòÉΓòÉΓòÉ 2.7. The LOCAL_EXECUTION_LINKS Entries ΓòÉΓòÉΓòÉ

Currently, these features of Lynx are disaabled in Lynx/2. The CFG file section
dealing with these is left here as a convenience for the author, in the event
that these are enabled in the future.


ΓòÉΓòÉΓòÉ 2.8. The INEWS Entry ΓòÉΓòÉΓòÉ

Set INEWS to the full path and name of your program for posting to newsgroups.
A "mini" inews,written in REXX, is included in the Lynx/2 distribution, and
will be used by default if this entry is commented out. You can disable news
posting by setting INEWS to "none", or via -restrictions switches.

#INEWS:inews


ΓòÉΓòÉΓòÉ 2.9. The VI_KEYS_ALWAYS_ON Entry ΓòÉΓòÉΓòÉ

VI_KEYS can be turned on by the user in the options screen or the .lynxrc file.
This is just the default.

VI_KEYS_ALWAYS_ON:FALSE


ΓòÉΓòÉΓòÉ 2.10. The EMACS_KEYS_ALWAYS_ON Entry ΓòÉΓòÉΓòÉ

EMACS_KEYS can be turned on by the user in the options screen or the .lynxrc
file. This is just the default.

EMACS_KEYS_ALWAYS_ON:FALSE


ΓòÉΓòÉΓòÉ 2.11. The DEFAULT_KEYPAD_MODE_IS_NUMBERS_AS_ARROWS Entry ΓòÉΓòÉΓòÉ

DEFAULT_KEYPAD_MODE specifies whether by default the user has numbers that work
like arrows or else numbered links DEFAULT KEYPAD MODE may be set to TRUE for
using numbers as arrows as default or FALSE for using numbered links as the
default.

DEFAULT_KEYPAD_MODE_IS_NUMBERS_AS_ARROWS:TRUE


ΓòÉΓòÉΓòÉ 2.12. The CASE_SENSITIVE_ALWAYS_ON Entry ΓòÉΓòÉΓòÉ

The default search type. This is a default that can be overridden by the user.

CASE_SENSITIVE_ALWAYS_ON:FALSE


ΓòÉΓòÉΓòÉ 2.13. The DEFAULT_BOOKMARK_FILE Entry ΓòÉΓòÉΓòÉ

DEFAULT_BOOKMARK_FILE is a default filename for use as a personal bookmark
file. It should start without a slash and will reference a file from the users
$HOME directory.

NOTE: A file ending in .htm should be used eliminate potential problems

DEFAULT_BOOKMARK_FILE:Bookmark.htm


ΓòÉΓòÉΓòÉ 2.14. The DEFAULT_USER_MODE Entry ΓòÉΓòÉΓòÉ

DEFAULT_USER_MODE sets the default user mode for Lynx users. NOVICE shows a
three line help message at the bottom of the screen. INTERMEDIATE shows normal
amount of help (one line). ADVANCED help is replaced by the URL of the current
link

DEFAULT_USER_MODE:NOVICE


ΓòÉΓòÉΓòÉ 2.15. The DEFAULT_EDITOR Entry ΓòÉΓòÉΓòÉ

DEFAULT_EDITOR sets the default editor for Lynx users. If an editor is defined
then the user may edit local documents using that editor. The editor will also
be used for sending mail messages. If no editor is defined here or by the user
the user will not be able to edit local documents and a primative line oriented
mail input mode will be used.

NOTE: Do not define an editor unless you know that every user will know how to
use it. Most users do not enjoy getting stuck in an unknown editor that they
can't get out of. Users can easily define an editor of their own using the
options menu, so it is not always desirable to set the DEFAULT_EDITOR.

DEFAULT_EDITOR: tedit


ΓòÉΓòÉΓòÉ 2.16. The SYSTEM_EDITOR Entry ΓòÉΓòÉΓòÉ

SYSTEM_EDITOR behaves the same as DEFAULT_EDITOR except that it can't be
changed.

SYSTEM_EDITOR:


ΓòÉΓòÉΓòÉ 2.17. The PREFERRED_LANGUAGE Entry ΓòÉΓòÉΓòÉ

PREFERRED_LANGUAGE is the language in MIME notation (e.g., "en", "fr") which
will be indicated by Lynx in its Accept-Language headers as the preferred
language. If available, the document will be transmitted in that language.
Users can override this setting via the 'o'ptions menu and save that preference
in their RC file.

PREFERRED_LANGUAGE:en


ΓòÉΓòÉΓòÉ 2.18. The Proxy Variables ΓòÉΓòÉΓòÉ

Lynx/2 supports the use of proxy servers that can act as firewall gateways and
caching servers. They are preferable to the older gateway servers. Each
protocol used by Lynx can be mapped separately using PROTOCOL_proxy environment
variables (see INSTALLATION). If you have not set them externally, you can set
them at run time via this configuration file. They will not override external
settings.

#http_proxy:http://some.server.dom:port/
#ftp_proxy:http://some.server.dom:port/
#gopher_proxy:http://some.server.dom:port/
#news_proxy:http://some.